Systems and methods for determining and utilizing customer energy profiles for load control for individual structures, devices, and aggregation of same

ABSTRACT

Systems and methods for managing electrical load control events in an electric power grid are disclosed. A server processor is operable to generate an energy consumption profile for each of the plurality of service points. Each energy consumption profile comprises energy consumption information for a plurality of controllable energy consuming devices. The server processor selects at least one service point from the plurality of service points based on a predetermined criterion and sends at least one load control event to the at least one service point in response to an energy reduction request. The server processor determines an energy saving resulting from the at least one load control event at the at least one service point. The energy saving is determined based on a monetary supply equivalent value for each of the plurality of controllable energy consuming devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application relates to and claims priority from the following U.S. patent applications. This application is a continuation of U.S. patent application Ser. No. 15/898,701, which is a continuation of U.S. patent application Ser. No. 14/790,555 filed Jul. 2, 2015 and issued as U.S. Pat. No. 9,899,836, which is a continuation of U.S. patent application Ser. No. 13/464,665 filed May 4, 2012 and issued as U.S. Pat. No. 9,177,323, which is a continuation-in-part of U.S. patent application Ser. No. 13/019,867 filed Feb. 2, 2011 and issued as U.S. Pat. No. 8,996,183. U.S. patent application Ser. No. 13/019,867 is a continuation-in-part of U.S. patent application Ser. No. 12/715,124 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,010,812, which is a division of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 13/019,867 is also a continuation-in-part of U.S. patent application Ser. No. 12/715,195 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,032,233, which is a division of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 13/019,867 is further a continuation-in-part of U.S. patent application Ser. No. 12/001,819 filed on Dec. 13, 2007, which is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 13/019,867 is further a continuation-in-part of U.S. patent application Ser. No. 12/775,979 filed on May 7, 2010 now U.S. Pat. No. 8,396,606. U.S. patent application Ser. No. 12/775,979 is a continuation-in-part of U.S. patent application Ser. No. 12/001,819 filed Dec. 12, 2007, which is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/775,979 is also a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/775,979 also claims priority under 35 U.S.C. § 119(e) upon U.S. Provisional Application No. 61/215,725 filed on May 8, 2009. U.S. patent application Ser. No. 13/019,867 is further a continuation-in-part of U.S. patent application Ser. No. 12/783,415 filed on May 19, 2010 now abandoned. U.S. patent application Ser. No. 12/783,415 is a continuation-in-part of U.S. patent application Ser. No. 12/715,124 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,010,812, which is a division of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/783,415 is also a continuation-in-part of U.S. patent application Ser. No. 12/001,819 filed on Dec. 13, 2007, which is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/783,415 also claims priority under 35 U.S.C. § 119(e) upon U.S. Provisional Application No. 61/216,712 filed on May 20, 2009. U.S. patent application Ser. No. 13/019,867 is a continuation-in-part of U.S. patent application Ser. No. 12/896,307 filed on Oct. 1, 2010 and issued as U.S. Pat. No. 8,527,107. U.S. patent application Ser. No. 12/896,307 is a continuation-in-part of U.S. patent application Ser. No. 12/715,124 filed Mar. 1, 2010 and issued as U.S. Pat. No. 8,010,812, which is a division of U.S. patent application Ser. No. 11/895,909 filed Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/896,307 is also a continuation-in-part of U.S. patent application Ser. No. 12/715,195 filed Mar. 1, 2010 and issued as U.S. Pat. No. 8,032,233, which is also a division of U.S. patent application Ser. No. 11/895,909 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/896,307 is further a continuation-in-part of U.S. patent application Ser. No. 12/702,640 filed Feb. 9, 2010 and issued as U.S. Pat. No. 8,131,403. U.S. patent application Ser. No. 12/702,640 is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/702,640 also claims priority upon U.S. Provisional Application No. 61/150,978 filed Feb. 9, 2009 and U.S. Provisional Application No. 61/176,752 filed May 8, 2009. U.S. patent application Ser. No. 12/896,307 further claims priority under 35 U.S.C. § 119(e) upon U.S. Provisional Application No. 61/279,072 filed on Oct. 15, 2009. All of the above mentioned documents are incorporated herein by reference in their entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates generally to electrical power load control systems and, more particularly, to creating customer profiles using energy consumption patterns.

2. Description of Related Art

Customer profiles are often used by systems for a variety of reasons. One reason is to promote customer loyalty. This involves keeping information about not only the customer, but about the customer's actions as well. This may include information about what the customer owns (i.e., which devices), how they are used, when they are used, etc. By mining this data, a company can more effectively select rewards for customers that give those customers an incentive for continuing to do business with the company. This is often described as customer relationship management (CRM).

Customer profile data is also useful for obtaining feedback about how a product is used. In software systems, this is often used to improve the customer/user experience or as an aid to testing. Deployed systems that have customer profiling communicate customer actions and other data back to the development organization. That data is analyzed to understand the customer's experience. Lessons learned from that analysis is used to make modifications to the deployed system, resulting in an improved system.

Customer profile data may also be used in marketing and sales. For instance, a retail business may collect a variety of information about a customer, including what customers look at on-line and inside “brick-and-mortar” stores. This data is mined to try to identify customer product preferences and shopping habits. Such data helps sales and marketing determine how to present products of probable interest to the customer, resulting in greater sales.

However, the collection of customer profile information by power utilities has been limited to customer account information. Because power utilities typically are unable to collect detailed data about what is happening inside a customer's home or business, including patterns of energy consumption by device, there has been little opportunity to create extensive customer profiles.

SUMMARY OF THE INVENTION

Embodiments described herein utilize the Active Load Management System (ALMS) that is fully described in commonly-owned published patent application US 2009/0062970. The ALMS captures energy usage data at each service point and stores that data in a central database. This data describes all of the energy consumed by devices owned by each customer, as well as additional information, such as customer preferences. Other embodiments of the ALMS focus on use of this information in the calculation of carbon credits or for the trading of unused energy.

In one embodiment, a system and method are provided for creating and making use of customer profiles, including energy consumption patterns. Devices within a service point, using the active load director, may be subject to control events, often based on customer preferences. These control events cause the service point to use less power. Data associated with these control events, as well as related environment data, are used to create an energy consumption profile for each service point. This can be used by the utility to determine which service points are the best targets for energy consumption. In addition, an additional algorithm determines how to prevent the same service points from being picked first each time the utility wants to conserve power.

In one embodiment, a method is provided for determining and using customer energy profiles to manage electrical load control events on a communications network between a server in communication with an electric utility and a client device at each of a plurality of service points. A customer profile is generated at the server for each of a plurality of customers including at least energy consumption information for a plurality of controllable energy consuming devices at an associated service point. The plurality of customer profiles is stored in a database at the server for use in load control events. The plurality of customer profiles are aggregated into a plurality of groups based on at least one predetermined criterion. A candidate list of service points for load control events based on the predetermined criterion is generated at the server. A load control event is sent to at least one selected service point in the candidate list of service points in response to an energy reduction request including a target energy savings received from the electric utility via the communications network. An energy savings for the plurality of controllable energy consuming devices resulting from the load control event at the selected service point is determined at the server. The server determines if the resulting energy savings is at least equal to the target energy savings. The load control event is sent to at least one selected additional service point in the candidate list of service points in order to reach the target energy savings, if the target energy savings has not been reached.

In one embodiment, a system is provided for determining and using customer energy profiles to manage electrical load control events on a communications network between a server in communication with an electric utility and a client device at each of a plurality of service points. The system includes a memory storing a database containing a plurality of customer profiles for load control events wherein each customer profile includes at least energy consumption information for a plurality of controllable energy consuming devices at an associated service point; and a server processor, cooperative with the memory, and configured for managing electrical load control events on the communications network to the plurality of service points by: generating a customer profile for each of a plurality of customers; aggregating the plurality of customer profiles into a plurality of groups based on at least one predetermined criterion; generating a candidate list of service points for load control events based on the predetermined criterion; sending a load control event to at least one selected service point in the candidate list of service points in response to an energy reduction request including a target energy savings received from the electric utility via the communications network; determining an energy savings for the plurality of controllable energy consuming devices resulting from the load control event at the selected service point; determining if the resulting energy savings is at least equal to the target energy savings; and sending the load control event to at least one selected additional service point in the candidate list of service points in order to reach the target energy savings.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other advantages and aspects of the embodiments of the invention will become apparent and more readily appreciated from the following detailed description of the embodiments taken in conjunction with the accompanying drawings, as follows.

FIG. 1 is a block diagram of an exemplary IP-based, Active Load Management System (ALMS).

FIG. 2 is a block diagram illustrating an exemplary active load director (ALD) server included in the active load management system.

FIG. 3 is a block diagram illustrating an exemplary active load client (ALC) included in the active load management system.

FIG. 4 is a graph illustrating how drift is calculated.

FIG. 5 is a graph illustrating how service points are selected for optimal drift.

FIG. 6 is an operational flow diagram illustrating an exemplary Intelligent Load Rotation algorithm.

DETAILED DESCRIPTION

Before describing in detail exemplary embodiments, it should be observed that the embodiments described reside primarily in combinations of apparatus components and processing steps related to actively managing power loading on an individual subscriber or service point basis, determining the customer profile of individual devices aggregated to related service points, and optionally tracking power savings incurred by both individual subscribers and an electric utility. Accordingly, the apparatus components and method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments disclosed so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term “electric utility” refers to any entity that generates and distributes electrical power to its customers, that purchases power from a power-generating entity and distributes the purchased power to its customers, or that supplies electricity created by alternative energy sources, such as solar power, wind power or otherwise, to power generation or distribution entities through the Federal Energy Regulatory Commission (FERC) electrical grid or otherwise. The present invention provides for systems and methods relating to an electric grid operator or any market participant associated with an electric grid, including retail electrical providers.

Embodiments of the invention include a number of novel concepts, including a customer profile, drift, and intelligent load rotation as more fully described below. A customer profile captures patterns of power consumption for each customer. The drift concept includes a method for calculating drift, which is important in estimating power savings within thermal control devices. The intelligent load rotation concept includes a method for selecting customers for utility-initiated control events using intelligent load rotation.

The embodiments described utilize concepts disclosed in commonly-owned published patent application US 2009/0062970, entitled “System and Method for Active Power Load Management” which is incorporated by reference in its entirety herein. The following paragraphs describe the Active Management Load System (ALMS), Active Load Director (ALD), and Active Load Client (ALC) in sufficient detail to assist the reader in the understanding of the embodiments described herein. More detailed description of the ALMS, ALD, and ALC can be found in US 2009/0062970.

It should be noted that control events and other messaging used in embodiments of the invention include regulated load management messages. Regulated load management messages contain information used to apply control of the electric supply to individual appliances or equipment on customer premises. The load to be controlled includes native load and operating reserves including regulating, spinning, and non-spinning types.

Active Load Management System

FIG. 1 depicts an exemplary IP-based Active Load Management System (ALMS) 10 that may be utilized by a utility in the embodiments described herein. The exemplary ALMS 10 monitors and manages power distribution via an active load director (ALD) 100 connected between one or more utility control centers (UCCs) 200 and one or more Active Load Clients (ALCs) 300. The ALD 100 may communicate with the utility control center 200 and each active load client 300 either directly or through a network 80 using the Internet Protocol (IP) or any other connection-based protocols. For example, the ALD 100 may communicate using RF systems operating via one or more base stations 90 using one or more well-known wireless communication protocols. Alternatively, or additionally, the ALD 100 may communicate via a digital subscriber line (DSL) capable connection, cable television based IP capable connection, or any combination thereof. In the exemplary embodiment shown in FIG. 1, the ALD 100 communicates with one or more active load clients 300 using a combination of traditional IP-based communication (e.g., over a trunked line) to a base station 90 and a wireless channel implementing the WiMax protocol for the “last mile” from the base station 90 to the active load client 300.

Each ALC 300 is accessible through a specified address (e.g., IP address) and controls and monitors the state of individual smart breaker modules or intelligent appliances 60 installed in the business or residence 20 to which the ALC 300 is associated (e.g., connected or supporting). Each ALC 300 is associated with a single residential or commercial customer. In one embodiment, the ALC 300 communicates with a residential load center 400 that contains smart breaker modules, which are able to switch from an “ON” (active) state to an “OFF” (inactive) state, and vice versa, responsive to signaling from the ALC 300. Typically, each smart breaker controls a single appliance (e.g., a washer/dryer 30, a hot water heater 40, an HVAC unit 50, or a pool pump 70).

Additionally, the ALC 300 may control individual smart appliances directly (e.g., without communicating with the residential load center 400) via one or more of a variety of known communication protocols (e.g., IP, Broadband over Power Line (BPL) in various forms, including through specifications promulgated or being developed by the HOMEPLUG Powerline Alliance and the Institute of Electrical and Electronics Engineers (IEEE), Ethernet, Bluetooth, ZigBee, Wi-Fi, WiMax, etc.). Additionally or alternatively to WiMax, other communications protocols may be used, including but not limited to a “1 G” wireless protocol such as analog wireless transmission, first generation standards based (IEEE, ITU or other recognized world communications standard), a “2-G” standards based protocoal such as “EDGE or CDMA 2000 also known as 1×RTT”, a 3G based standard such as “High Speed Packet Access (HSPA) or Evolution for Data Only (EVDO), any accepted 4G standard such as “IEEE, ITU standards that include WiMax, Long Term Evolution “LTE” and its derivative standards, any Ethernet solution wireless or wired, or any proprietary wireless or power line carrier standards that communicate to a client device or any controllable device that sends and receives an IP based message.

Typically, a smart appliance 60 includes a power control module (not shown) having communication abilities. The power control module is installed in-line with the power supply to the appliance, between the actual appliance and the power source (e.g., the power control module is plugged into a power outlet at the home or business and the power cord for the appliance is plugged into the power control module). Thus, when the power control module receives a command to turn off the appliance 60, it disconnects the actual power supplying the appliance 60. Alternatively, a smart appliance 60 may include a power control module integrated directly into the appliance, which may receive commands and control the operation of the appliance directly (e.g., a smart thermostat may perform such functions as raising or lowering the set temperature, switching an HVAC unit on or off, or switching a fan on or off).

Also as shown in FIG. 1, a service point 20 may have its own power generation on-site, including solar panels, fuel cells, or wind turbines. This is indicated by the power generating device 96. The power generating device 96 connects to the Active Load Client 300. Power that is added by the power generating device 96 is added to the overall utility capacity. The utility provides credit to the service point owner based on the energy produced at the service point.

The service point 20 also contains the Customer Dashboard 98. This is a web-based interface used by the customer to specify preferences for the use of the Active Load Management System at the customer's service point. These preferences include control event preferences, bill management preferences, and others.

Active Load Director

Referring now to FIG. 2, the ALD 100 may serve as the primary interface to customers, as well as to service personnel. In the exemplary embodiment depicted in FIG. 2, the ALD 100 includes a utility control center (UCC) security interface 102, a UCC command processor 104, a master event manager 106, an ALC manager 108, an ALC security interface 110, an ALC interface 112, a web browser interface 114, a customer sign-up application 116, customer personal settings 138, a customer reports application 118, a power savings application 120, an ALC diagnostic manager 122, an ALD database 124, a service dispatch manager 126, a trouble ticket generator 128, a call center manager 130, a carbon savings application 132, a utility power and carbon database 134, a read meter application 136, and a security device manager 140.

In one embodiment, customers interact with the ALD 100 using the web browser interface 114, and subscribe to some or all of the services offered by the power load management system 10 via a customer sign-up application 116. In accordance with the customer sign-up application 116, the customer specifies customer personal settings 138 that contain information relating to the customer and the customer's residence or business, and defines the extent of service to which the customer wishes to subscribe. Customers may also use the web browser interface 114 to access and modify information pertaining to their existing accounts.

The ALD 100 also includes a UCC security interface 102 which provides security and encryption between the ALD 100 and a utility company's control center 200 to ensure that no third party is able to provide unauthorized directions to the ALD 100. A UCC command processor 104 receives and sends messages between the ALD 100 and the utility control center 200. Similarly, an ALC security interface 110 provides security and encryption between the ALD 100 and each ALC 300 on the system 10, ensuring that no third parties can send directions to, or receive information from, the ALC 300. The security techniques employed by the ALC security interface 110 and the UCC security interface 102 may include conventional symmetric key or asymmetric key algorithms, or proprietary encryption techniques.

The master event manager 106 maintains the overall status of the power load activities controlled by the power management system 10. The master event manager 106 maintains a separate state for each utility that is controlled and tracks the current power usage within each utility. The master event manager 106 also tracks the management condition of each utility (e.g., whether or not each utility is currently being managed). The master event manager 106 receives instructions in the form of transaction requests from the UCC command processor 104 and routes instructions to components necessary to complete the requested transaction, such as the ALC manager 108 and the power savings application 120.

The ALC manager 108 routes instructions between the ALD 100 and each ALC 300 within the system 10 through an ALC interface 112. For instance, the ALC manager 108 tracks the state of every ALC 300 serviced by specified utilities by communicating with the ALC 300 through an individual IP address. The ALC interface 112 translates instructions (e.g., transactions) received from the ALC manager 108 into the proper message structure understood by the targeted ALC 300 and then sends the message to the ALC 300. Likewise, when the ALC interface 112 receives messages from an ALC 300, it translates the message into a form understood by the ALC manager 108 and routes the translated message to the ALC manager 108.

The ALC manager 108 receives from each ALC 300 that it services, either periodically or responsive to polling messages sent by the ALC manager 108, messages containing the present power consumption and the status (e.g., “ON” or “OFF”) of each device controlled by the ALC 300. Alternatively, if individual device metering is not available, then the total power consumption and load management status for the entire ALC 300 may be reported. The information contained in each status message is stored in the ALD database 124 in a record associated with the specified ALC 300. The ALD database 124 contains all the information necessary to manage every customer account and power distribution. In one embodiment, the ALD database 124 contains customer contact information and associated utility companies for all customers having ALCs 300 installed at their residences or businesses, as well as a description of specific operating instructions for each managed device (e.g., IP-addressable smart breaker or appliance), device status, and device diagnostic history.

Another message that can be exchanged between an ALC 300 and the ALC manager 108 is a status response message. A status response message reports the type and status of each device controlled by the ALC 300 to the ALD 100. When a status response message is received from an ALC 300, the ALC manager 108 logs the information contained in the message in the ALD database 124.

In one embodiment, upon receiving instructions (e.g., a “Cut” instruction) from the master event manager 106 to reduce power consumption for a specified utility, the ALC manager 108 determines which ALCs 300 and/or individually controlled devices to switch to the “OFF” state based upon present power consumption data stored in the ALD database 124. The ALC manager 108 then sends a message to each selected ALC 300 containing instructions to turn off all or some of the devices under the ALC's control.

A read meter application 136 may be optionally invoked when the UCC command processor 104 receives a “Read Meters” or equivalent command from the utility control center 200. The read meter application 136 cycles through the ALD database 124 and sends a read meter message or command to each ALC 300, or to ALCs 300 specifically identified in the UCC's command, via the ALC manager 108. The information received by the ALC manager 108 from the ALC 300 is logged in the ALD database 124 for each customer. When all the ALC meter information has been received, the information is sent to the requesting utility control center 200 using a business to business (e.g., ebXML) or other desired protocol.

Active Load Client

FIG. 3 illustrates a block diagram of an exemplary active load client 300 in accordance with one embodiment of the present invention. The depicted active load client 300 includes a smart breaker module controller 306, a communications interface 308, a security interface 310, an IP-based communication converter 312, a device control manager 314, a smart breaker (B1-BN) counter manager 316, an IP router 320, a smart meter interface 322, a smart device interface 324, an IP device interface 330, and a power dispatch device interface 340. The active load client 300, in this embodiment, is a computer or processor-based system located on-site at a customer's residence or business. The primary function of the active load client 300 is to manage the power load levels of controllable, power consuming load devices located at the residence or business, which the active load client 300 oversees on behalf of the customer. In an exemplary embodiment, the active load client 300 may include dynamic host configuration protocol (DHCP) client functionality to enable the active load client 300 to dynamically request IP addresses for itself and/or one or more controllable devices 402-412, 60 managed thereby from a DHCP server on the host IP network facilitating communications between the active load client 300 and the ALD 100. The active load client 300 may further include router functionality and maintain a routing table of assigned IP addresses in a memory of the active load client 300 to facilitate delivery of messages from the active load client 300 to the controllable devices 402-412, 60. Finally, the power generation device 96 at the service point 20 sends data about power generated to the power dispatch device interface 340.

A communications interface 308 facilitates connectivity between the active load client 300 and the ALD server 100. Communication between the active load client 300 and the ALD server 100 may be based on any type of IP or other connection protocol including, but not limited to, the WiMax protocol. Thus, the communications interface 308 may be a wired or wireless modem, a wireless access point, or other appropriate interface.

A standard IP Layer-3 router 320 routes messages received by the communications interface 308 to both the active load client 300 and to any other locally connected device 440. The router 320 determines if a received message is directed to the active load client 300 and, if so, passes the message to a security interface 310 to be decrypted. The security interface 310 provides protection for the contents of the messages exchanged between the ALD server 100 and the active load client 300. The message content is encrypted and decrypted by the security interface 310 using, for example, a symmetric encryption key composed of a combination of the IP address and GPS data for the active load client 300 or any other combination of known information. If the message is not directed to the active load client 300, then it is passed to the IP device interface 330 for delivery to one or more locally connected devices 440. For example, the IP router 320 may be programmed to route power load management system messages as well as conventional Internet messages. In such a case, the active load client 300 may function as a gateway for Internet service supplied to the residence or business instead of using separate Internet gateways or routers.

An IP based communication converter 312 opens incoming messages from the ALD server 100 and directs them to the appropriate function within the active load client 300. The converter 312 also receives messages from various active load client 300 functions (e.g., a device control manager 314, a status response generator 304, and a report trigger application 318), packages the messages in the form expected by the ALD server 100, and then passes them on to the security interface 310 for encryption.

The device control manager 314 processes power management commands for various controllable devices logically connected to the active load client 300. The devices can be either smart breakers 402-412 or other IP based devices 60, 460, such as smart appliances with individual control modules (not shown). The device control manager 314 also processes “Query Request” or equivalent commands or messages from the ALD server 100 by querying a status response generator 304 which maintains the type and status of each device controlled by the active load client 300, and providing the status of each device to the ALD server 100.

The status response generator 304 receives status messages from the ALD server 100 and, responsive thereto, polls each controllable device 402-412, 60, 460 under the active load client's control to determine whether the controllable device 402-412, 60, 460 is active and in good operational order. Each controllable device 402-412, 60, 460 responds to the polls with operational information (e.g., activity status and/or error reports) in a status response message. The active load client 300 stores the status responses in a memory associated with the status response generator 304 for reference in connection with power reduction events.

The smart device interface 324 facilitates IP or other address-based communications to individual devices 60 (e.g., smart appliance power control modules) that are attached to the active load client 300. The connectivity can be through one of several different types of networks including, but not limited to, BPL, ZigBee, Wi-Fi, Bluetooth, or direct Ethernet communications. Thus, the smart device interface 324 is a modem adapted for use in or on the network connecting the smart devices 60 to the active load client 300.

The smart breaker module controller 306 formats, sends, and receives messages to and from the smart breaker module 400. In one embodiment, the communications is preferably through a BPL connection. In such embodiment, the smart breaker module controller 306 includes a BPL modem and operations software. The smart breaker module 400 contains individual smart breakers 402-412, wherein each smart breaker 402-412 includes an applicable modem (e.g., a BPL modem when BPL is the networking technology employed) and is preferably in-line with power supplied to a single appliance or other device. The B1-BN counter manager 316 determines and stores real time power usage for each installed smart breaker 402-412. For example, the counter manager 316 tracks or counts the amount of power used by each smart breaker 402-412 and stores the counted amounts of power in a memory of the active load client 300 associated with the counter manager 316.

The smart meter interface 322 manages either smart meters 460 that communicate using BPL or a current sensor 452 connected to a traditional power meter 450. When the active load client 300 receives a “Read Meters” command or message from the ALD server 100 and a smart meter 460 is attached to the active load client 300, a “Read Meters” command is sent to the meter 460 via the smart meter interface 322 (e.g., a BPL modem). The smart meter interface 322 receives a reply to the “Read Meters” message from the smart meter 460, formats this information along with identification information for the active load client 300, and provides the formatted message to the IP based communication converter 312 for transmission to the ALD server 100.

Customer Profiles

The embodiments disclosed make use of the “customer profiles” concept. The ALMS enables data to be gathered to generate a profile of each customer, including information about controllable energy consuming devices, and the related individual structures or service points. Customer profiles reside within the Active Load Director Database 124 in the Active Load Director 100. Included in this customer profile is the customer's pattern of energy consumption. The customer profile includes, but is not limited to, the following: (1) customer name; (2) customer address; (3) geodetic location; (4) meter ID; (5) customer programs (possibly including program history); (6) device information, including device type and manufacturer/brand; (7) customer energy consumption patterns; and (8) connection and disconnection profile. The connection/disconnection profile can include service priority (i.e., elderly, police, etc.) and disconnection instructions.

The customer profile is created by using data gathered from within the ALMS. Data gathered or calculated includes, but is not be limited to, the following: (1) set points; (2) energy and average energy used in a given time period; (3) energy and average energy saved in a given time period; (4) drift time per unit temperature and average drift time; and (5) power time per unit temperature and average power time per unit temperature.

In other embodiments, additional data called “variability factors” may be captured by the ALMS as part of the customer profile, including, but not limited to, the following: (1) outside temperature, (2) sunlight, (3) humidity, (4) wind speed and direction, (5) elevation above sea level, (6) orientation of the service point structure, (7) duty duration and percentage, (8) set point difference, (9) current and historic room temperature, (10) size of structure, (11) number of floors, (12) type of construction (brick, wood, siding etc.) (13) color of structure, (14) type of roofing material and color, (15) construction surface of structure (built on turf, clay, cement, asphalt etc.), (16) land use (urban, suburban, rural), (17) latitude/longitude, (18) relative position to jet stream, (19) quality of power to devices, (20) number of people living in and/or using structure and (21) other environmental factors.

Additional factors may also be deemed necessary for determining unique energy consumption patterns and generating performance curves and data matrices for usage in load control events and other purposes detailed in this and related patent applications.

By way of example, based upon the reduction in consumed power, the systems and methods of the present invention provide for generating at the control center a power supply value (PSV) corresponding to the reduction in consumed power by the power consuming device(s). Importantly, the PSV is an actual value that includes measurement and verification of the reduction in consumed power; such measurement and verification methods may be determined by the appropriate governing body or authority for the electric power grid(s). Power Supply Value (PSV) is calculated at the meter or submeter or at building control system or at any device or controller that measures power within the standard as supplied by the regulatory body(ies) that govern the regulation of the grid. PSV variations may depend on operating tolerances, operating standard for accuracy of the measurement. The PSV enables transformation of curtailment or reduction in power at the device level by any system that sends or receives an IP message to be related to or equated to supply as presented to the governing entity that accepts these values and award supply equivalence, for example of a power generating entity or an entity allowed to control power consuming devices as permitted by the governing body of the electric power grid, e.g., FERC, NERC, etc.

PSV may be provided in units of electrical power flow, monetary equivalent, and combinations thereof. Thus, the PSV provides an actual value that is confirmed by measurement and/or verification, thereby providing for a curtailment value as a requirement for providing supply to the power grid, wherein the supply to the power electric power grid is provided for grid stability, voltage stability, reliability, and combinations thereof, and is further provided as responsive to an energy management system or equivalent for providing grid stability, reliability, frequency as determined by governing authority for the electric power grid and/or grid operator(s).

As part of the Active Load Directory (ALD), the methods described herein consolidate this information creating a historic energy consumption pattern reflecting the amount of energy used by each service point to maintain its normal mode of operation. This energy consumption pattern is part of a customer's profile.

Energy consumption patterns are subject to analysis that may be used for a variety of different types of activities. For example, based on the energy consumption patterns created from this data, the ALD will derive performance curves and/or data matrices for each service point to which the Active Load Management System is attached and determine the amount of energy reduction that can be realized from each service point. The ALD will create a list of service points through which energy consumption can be reduced via demand side management, interruptible load, or spinning/regulation reserves. This information can be manipulated by the ALD processes to create a prioritized, rotational order of control, called “intelligent load rotation” which is described in detail below. This rotational shifting of the burden of the interruptible load has the practical effect of reducing and flattening the utility load curve while allowing the serving utility to effectively group its customers within the ALD or its own databases by energy efficiency.

The practical application of this data is that in load control events, a utility can determine the most efficient service points to dispatch energy from, or more importantly derive the most inefficient service points (e.g., homes, small businesses, communities, structures, or devices) within the utility's operating territory. Based on this information, highly targeted conservation programs could have an immediate impact to improve energy efficiency. From a marketing perspective, this is invaluable information because it contains the comfort preference of a service point compared against the capabilities of the service point's energy consuming devices, or the lack of efficiency of those devices. From a national security point of view, the profiles could be used to determine habits of monitored end customers in a similar fashion to how Communications Assistance for Law Enforcement Act (CALEA) is used by law enforcement for wire-tapping. Utilities may use energy consumption patterns to categorize or group customers for service, control event, marketing, sales, or other purposes. Other uses of energy consumption patterns are possible that determine or predict customer behavior.

Generally, the embodiments described encompass a closed loop system and method for creating a customer profile, calculating and deriving patterns of energy drift, and making use of those patterns when implemented through the machinery of a system comprised of load measurement devices combined with the physical communications link and when these inputs are manipulated through a computer, processor, memory, routers and other necessary machines as those who are skilled in the art would expect to be utilized.

Drift

The embodiments described also make use of the concept of “drift.” The data gathered for the customer profile is used to empirically derive the decay rate or drift, temperature slope, or a dynamic equation (f{x}) whereby the service point (or device) will have a uniquely derived “fingerprint” or energy usage pattern.

Drift occurs when a climate-controlled device begins to deviate from a set point. This may occur both normally and during control events. Customers define the upper and lower boundaries of comfort in customer preferences, with the set point in the middle of those boundaries. During normal operation, a climate controlled device will attempt to stay near the device's set point. However, all devices have a duty cycle that specifies when the device is in operation because many devices are not continuously in operation. For a climate-controlled device, the duty cycle ends when the inside temperature reaches, or is within a given tolerance of, the set point. This allows the device to “drift” (upward or downward) toward a comfort boundary temperature. Once the boundary temperature is reached, the duty cycle begins again until the inside temperature reaches, or is within a given tolerance of, the set point which ends the duty cycle.

Therefore, drift is the time it takes for a climate-controlled device to move from the set point to the upper or lower comfort boundary. Drift is calculated and recorded for each service point and for each device associated with the service point. The inverse of drift is “power time” which is the time it takes for the device to move from the comfort boundary to the set point.

Drift may also occur during a control event. A control event is an action that reduces or terminates power consumption of a device. During a control event, a climate-controlled device will drift toward maximum or minimum control event boundaries (upper or lower) until it reaches that boundary which is normally outside the comfort boundary. Once it reaches the control event boundary, the ALMS returns power to the device to enable it to reach the set point again.

As an example, an HVAC system may have a set point of 72 degrees and a minimum and maximum temperature of 68 degrees and 76 degrees, respectively. On a cold day, a control event would cause the HVAC system to begin to lose power and move toward the minimum temperature. Once the structure reaches the minimum temperature, the control event would end, and power would be restored to the HVAC system, thus causing the temperature to rise toward the preferred temperature. A similar but opposite effect would take place on a warm day.

In some embodiments, drift, as well as other measurements available from the active load director data base 124, are used to create an energy consumption pattern for each service point. Additional measurements may include vacancy times, sleep times, times in which control events are permitted, as well as variability factors referred to previously.

A device that resides within an energy-efficient structure will have a tendency to cool or heat more slowly, thus exhibiting a lower rate of drift. These devices may be subject to control events for longer periods of time, commensurate with the rate of drift, because it takes them longer to drift to a comfort boundary.

In another embodiment, the active load director server 100 identifies service points that have an optimum drift for power savings. The power savings application 120 calculates drift for each service point and saves that information in the active load director data base 124.

Intelligent Load Rotation

The embodiments disclosed also make use of the “intelligent load rotation” concept. Intelligent load rotation uses machine intelligence to ensure that the same service points are not always selected for control events, but distributes control events over a service area in some equitable way.

There are a variety of ways in which intelligent load rotation may be implemented. In one embodiment of intelligent load rotation, service points are simply selected in a sequential list until the end is reached, after which selection starts at the top of the list again. This is a fairly straightforward approach that may be implemented by any one skilled in the art.

FIG. 6 illustrates an operational flow diagram of the basic intelligent load rotation algorithm 1800. All other embodiments of intelligent load rotation are based on this embodiment. In general, the algorithm goes through each service point within a group of service points, and sends control events to each of those service points until enough energy savings have been obtained.

In its most basic form, the algorithm first identifies a group selection criteria as indicated in logic block 1802. This may be as simple as all service points or may be more complex, such as selecting service points within a specified drift or within a specified geographic area. The group selection criteria may include, but is not limited to, any of the following: (1) random selection of service points; (2) drift; (3) grouping of logical geodetic points by a utility; (4) efficiency rating of appliances; (5) ALD customer preferences; (6) capacity of devices; (7) proximity to transmission lines; (8) pricing signals (both dynamic and static); and (9) service priority, based upon an emergency situation (i.e. fire, police, hospital, elderly, etc.).

The algorithm then identifies an individual service point selection criterion as indicated in logic block 1804. This is the criterion for selecting individual service points within a group. In its simplest embodiment, this criterion involves sequential selection of service points within the group. Other criteria may include random selection, selection based on number of previous control events, or other criteria.

Next, the algorithm creates a candidate list of service points based on the group selection criteria as indicated in logic block 1806. From this list, the algorithm selects a service point based on the individual service point selection criteria as indicated in logic block 1810. The ALMS then sends a control event to the selected service point as indicated in logic block 1814, and calculates the energy savings of that control event based on drift calculation as indicated in block 1816. The algorithm then determines if more energy savings are needed to reach the savings target as indicated in decision block 1820. If not, then the ALMS records where the algorithm ended in the candidate list as indicated in block 1824 and exits. If more energy savings are needed, then the ALMS determines if any more service points are in the candidate list as indicated in decision block 1830. If there are no more service points in the candidate list, then the algorithm returns to the beginning of the candidate list again in logic block 1840. Otherwise, if there are more service points in the candidate list, the algorithm simply returns to logic block 1810.

In an alternate embodiment, decision block 1820 may be modified to determine if more service points are to be selected from this group.

There are many other embodiments of intelligent load rotation. Many embodiments are based on the group selection criteria. Service points may be grouped by geography or some other common characteristic of service points. For example, groups might include “light consumers” (because they consume little energy), “daytime consumers” (because they work at night), “swimmers” (for those who have a pool and use it), or other categories. These categories are useful to the utility for quickly referring to customers with specific energy demographics. The utility may then select a number of service points in each group for control events to spread control events among various groups.

In another embodiment, optimum drift can be used as the group selection criteria. Because those service points will use the least energy, the utility may want to select those service points that are the most energy efficient.

In another embodiment, a group of service points is selected that have had the fewest control events in the past. This ensures that service points with the most control events in the past will be bypassed in favor of those who have received fewer control events.

In another embodiment, with reference to FIGS. 4-5, drift is used as a means of intelligent load rotation. As data is collected by the ALMS, it is possible to calculate the total drift of a device over time, as shown in FIG. 4. The calculation for one service point represents one vector on the graph. Each vector represents the drift for a single service point. To identify the service points with the optimal drift, the ALD 100 determines the median drift and all service points having a drift that is within one standard deviation away from that median. That represents the shaded area in the graph depicted in FIG. 5. If sufficient service points cannot be found that are within one standard deviation, then the second standard deviation can be selected.

In another embodiment, energy consumption patterns in customer profiles are used to identify service points that are the best targets for excess power sharing. This would occur when renewable energy such as solar or wind is added to the grid, resulting in power that cannot be compensated for by the grid. This could occur, for example, on very windy days. When this happens, utilities are faced with the problem of what to do with the excess energy. Instead of cutting power to service points in order to affect power savings, a utility could add energy to service points in order to effect power dissipation. The service points selected by the utility may be different (or even the inverse) of those selected for power savings. The devices at these service points would be turned on if they were off or set points for climate-controlled devices would be adjusted to heat or cool more than normal. Spread out over many control points, this can provide the energy dissipation needed.

In a further embodiment, energy consumption patterns within customer profiles could be used to identify opportunities for up selling, down selling, or cross selling. These opportunities may be determined by the power utility or by its partners. Data from customer profiles may be used to provide insights on inefficient devices, defective devices, or devices that require updating to meet current standards. Customer profile data may also be used to identify related sales opportunities. For example, if energy consumption patterns suggest that the customer may be very interested in personal energy conservation, then sales efforts could be directed toward that individual concerning products related to that lifestyle. This information can be used by the utility or its partners to provide incentives to customers to buy newer, updated devices, or obtain maintenance for existing devices. The customer is given the option to opt out of having his customer profile used for sales and marketing efforts, or for regulating energy conservation. The customer profile makes use of open standards (such as the CPExchange standard) that specify a privacy model with the customer profile. The use of consumption patterns in this manner is governed by national, state, or local privacy laws and regulations.

A further embodiment of using customer profiles to identify sales opportunities involves the use of device information to create incentives for customers to replace inefficient devices. By identifying the known characteristics and/or behavior of devices within a service point, the invention identifies those customers who may benefit from replacement of those devices. The invention estimates a payback period for replacement. This information is used by the ALMS operator to create redemptions, discounts, and campaigns to persuade customers to replace their devices.

It should be noted that many terms and acronyms are used in this description that are well-defined in the telecommunications and computer networking industries and are well understood by persons skilled in these arts. Complete descriptions of these terms and acronyms, whether defining a telecommunications standard or protocol, can be found in readily available telecommunications standards and literature and are not described in any detail herein.

As used in the foregoing description, the term “ZigBee” refers to any wireless communication protocol adopted by the Institute of Electrical and Electronics Engineers (IEEE) according to standard 802.15.4 or any successor standard(s), and the term “Bluetooth” refers to any short-range communication protocol implementing IEEE standard 802.15.1 or any successor standard(s). The term “High Speed Packet Data Access (HSPA)” refers to any communication protocol adopted by the International Telecommunication Union (ITU) or another mobile telecommunications standards body referring to the evolution of the Global System for Mobile Communications (GSM) standard beyond its third generation Universal Mobile Telecommunications System (UMTS) protocols. The term “Long Term Evolution (LTE)” refers to any communication protocol adopted by the ITU or another mobile telecommunications standards body referring to the evolution of GSM-based networks to voice, video and data standards anticipated to be replacement protocols for HSPA. The term “Code Division Multiple Access (CDMA) Evolution Date-Optimized (EVDO) Revision A (CDMA EVDO Rev. A)” refers to the communication protocol adopted by the ITU under standard number TIA-856 Rev. A.

It will be appreciated that embodiments or components of the systems described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions for managing power load distribution, and tracking and controlling individual subscriber power consumption and savings in one or more power load management systems. The non-processor circuits may include, but are not limited to, radio receivers, radio transmitters, antennas, modems, signal drivers, clock circuits, power source circuits, relays, meters, smart breakers, current sensors, and customer input devices. As such, these functions may be interpreted as steps of a method to distribute information and control signals between devices in a power load management system. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein. Further, it is expected that one of ordinary skill in the art, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein, will be readily capable of generating such software instructions, programs and integrated circuits (ICs), and appropriately arranging and functionally integrating such non-processor circuits, without undue experimentation.

In the foregoing specification, the invention has been described with reference to specific embodiments. However, one of ordinary skill in the art will appreciate that various modifications and changes may be made without departing from the scope of the present invention as set forth in the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention.

The corresponding structures, materials, acts, and equivalents of all means plus function elements in any claims below are intended to include any structure, material, or acts for performing the function in combination with other claim elements as specifically claimed.

In addition, it is possible to use some of the features of the embodiments disclosed without the corresponding use of the other features. Accordingly, the foregoing description of the exemplary embodiments is provided for the purpose of illustrating the principles of the invention, and not in limitation thereof, since the scope of the present invention is defined solely by the appended claims. 

What is claimed is:
 1. A system for managing electrical load control events in an electric power grid, comprising: a server processor coupled with a database in network communication with a plurality of service points; wherein each of the plurality of service points is associated with at least one management device and at least one power consuming device; wherein a customer profile is associated with each of the at least one management device, wherein the customer profile includes preference data for the at least one power consuming device; wherein the server processor receives at least one energy reduction request, including a target energy saving from at least one electric grid operator; wherein, in response to the at least one energy reduction request, the server processor is operable to send at least one load control event to the at least one management device associated with at least one of the plurality of service points; wherein the at least one management device is operable to turn off the at least one power consuming device, based on the preference data of the customer profile associated with the at least one management device; and wherein the server processor is operable to determine an energy saving resulting from the at least one load control event at the at least one of the plurality of service points, wherein the energy saving is determined based on a value for each of the at least one power consuming devices, wherein the value is based on a transformation of a measurement and verification of a reduction in consumed power by the at least one power consuming device.
 2. The system of claim 1, wherein the at least one power consuming device includes at least one Heating, Ventilation, and Air Conditioning (HVAC) unit.
 3. The system of claim 2, wherein the preference data includes at least one temperature set point for the at least one HVAC unit, energy used in a given time period, average energy used in the given time period, drift time per unit temperature, average drift time, power time per unit temperature, and/or average power time per unit temperature.
 4. The system of claim 1, wherein the customer profile includes a customer name, customer address, location data for the at least one management device associated with the customer profile, device information, and/or customer energy consumption patterns.
 5. The system of claim 1, wherein the at least one management device includes at least one smart thermostat.
 6. The system of claim 1, wherein the at least one management device is further constructed and configured for communication with a database, wherein the database generates a curtailment value for the at least one power consuming device based on the measurement and verification.
 7. The system of claim 6, wherein the curtailment value is accepted as supply by at least one governing entity.
 8. The system of claim 1, wherein the server processor selects the at least one of the plurality of service points based on preference data of the customer profile associated with the at least one management device associated with the at least one of the plurality of service points.
 9. A system for managing power on an electric power grid, comprising: a server processor coupled with a database in network communication with a plurality of service points; wherein each of the plurality of service points is associated with at least one management device and at least one power consuming device; wherein the at least one power consuming device includes at least one Heating, Ventilation, and Air Conditioning (HVAC) unit; wherein a customer profile is associated with each of the at least one management device, wherein the customer profile includes preference data for the at least one power consuming device; wherein the server processor receives at least one energy reduction request, including a target energy saving from at least one electric grid operator; wherein, in response to the at least one energy reduction request, the server processor is operable to send at least one load control event to the at least one management device associated with at least one of the plurality of service points; wherein the at least one management device is operable to turn off the at least one power consuming device, based on the preference data of the customer profile associated with the at least one management device; and wherein the server processor is operable to determine an energy saving resulting from the at least one load control event at the at least one of the plurality of service points.
 10. The system of claim 9, wherein the energy saving is determined based on a value for each of the at least one power consuming devices, wherein the value is based on a transformation of a measurement and verification of a reduction in consumed power by the at least one power consuming device.
 11. The system of claim 10, wherein the measurement and verification is performed by a smart meter.
 12. The system of claim 9, wherein the preference data includes at least one temperature set point for the at least one HVAC unit, energy used in a given time period, average energy used in the given time period, drift time per unit temperature, average drift time, power time per unit temperature, and/or average power time per unit temperature.
 13. The system of claim 9, wherein the customer profile includes a customer name, customer address, location data for the at least one management device associated with the customer profile, device information, and/or customer energy consumption patterns.
 14. The system of claim 9, wherein the at least one management device includes at least one smart thermostat.
 15. The system of claim 9, wherein the at least one management device is further constructed and configured for communication with a database, wherein the database generates a curtailment value for the at least one power consuming device based on the measurement and verification.
 16. The system of claim 15, wherein the curtailment value is accepted as supply by at least one governing entity.
 17. A system for managing power on an electric power grid, comprising: a server processor coupled with a database in network communication with a plurality of service points; wherein each of the plurality of service points is associated with at least one management device and at least one power consuming device; wherein the at least one management device includes at least one smart thermostat; wherein the at least one power consuming device includes at least one Heating, Ventilation, and Air Conditioning (HVAC) unit; wherein a customer profile is associated with each of the at least one management device, wherein the customer profile includes preference data for the at least one power consuming device; wherein the preference data includes at least one temperature set point for the at least one HVAC unit; wherein the server processor receives at least one energy reduction request, including a target energy saving from at least one electric grid operator; wherein, in response to the at least one energy reduction request, the server processor is operable to send at least one load control event to the at least one management device associated with at least one of the plurality of service points; and wherein the at least one management device is operable to turn off the at least one power consuming device, based on the preference data of the customer profile associated with the at least one management device.
 18. The system of claim 17, wherein the server processor is operable to determine an energy saving resulting from the at least one load control event at the at least one of the plurality of service points.
 19. The system of claim 18, wherein the energy saving is determined based on a value for each of the at least one power consuming devices, wherein the value is based on a transformation of a measurement and verification of a reduction in consumed power by the at least one power consuming device.
 20. The system of claim 17, wherein the at least one management device is further constructed and configured for communication with a database, wherein the database generates a curtailment value for the at least one power consuming device based on the measurement and verification, wherein the curtailment value is accepted as supply by at least one governing entity. 